From bbb5b2653a6bc9316443bd6e26e72aed997a8227 Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Wed, 5 Aug 2026 15:09:20 +0000 Subject: [PATCH] Add example query of A-Record groom scans to EVENTS doc --- doc/src/tables/events.m4 | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/doc/src/tables/events.m4 b/doc/src/tables/events.m4 index 95cb57d..46f7a37 100644 --- a/doc/src/tables/events.m4 +++ b/doc/src/tables/events.m4 @@ -224,6 +224,29 @@ The following table lists these rules and implications: For attendance grooming interval sampling events, the EVENTS.\ |EVENTS.Certainty| column must be ``sdb_identity_certain``. + The |DYADS| view is useful when querying attendance scan interval + groomings. + + .. code-block:: sql + :caption: + Using DYADS to query attendance scan interval groomings + + SELECT dyads.wid + , dyads.eid + , dyads.actor_pid, dyads.recipient_pid + , dyads.date + , dyads.animid + , dyads.commid + , dyads.start AS time + , dyads.actor, dyads.recipient + , dyads.style + , dyads.notes + , dyads.event_notes + FROM dyads + WHERE dyads.behavior = 'sdb_groom_scan_a' + ORDER BY dyads.actor, dyads.date, dyads.start + , dyads.recipient, dyads.eid; + .. _EVENTS_arrival_code: -- 2.34.1